Fix #169 - Files with very long paths fail to extract on Windows #170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Uses robocopy instead of copy to be able to deal with paths over 260 characters long. Smooths out robocopy's exit codes of 0-3 to become 0 (0-3 indicate successful exits with varying meanings, but typically you'd see an exit code of 1 for a successful fresh copy) - so that chef doesn't think the copy failed under those success scenarios.
This does mean that this will not work on older Windows versions unless the user installs robocopy separately. According to https://en.wikipedia.org/wiki/Robocopy#Versions and https://technet.microsoft.com/en-us/library/cc733145(v=ws.11).aspx it's been bundled in Windows Server 2008 &2012; Windows Vista, 7, 8, 8.1, and 10. Given that range, I think it's still a relatively good choice.
Issues Resolved
Check List